chore(deps): update dependency pyparsing to v3.3.2#834
chore(deps): update dependency pyparsing to v3.3.2#834renovate-bot wants to merge 1 commit intogoogleapis:mainfrom
Conversation
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request updates the Highlights
Changelog
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request updates the pyparsing dependency from version 3.2.5 to 3.3.2. This update brings performance improvements and new warning classes. It is important to note that pyparsing versions 3.3.0 and above will emit DeprecationWarnings for non-PEP8 compliant method names. Please ensure that the project's code base is compatible with these changes and consider updating any legacy API calls to their PEP8-compliant equivalents to avoid future warnings.
Note: Security Review has been skipped due to the limited scope of the PR.
| pyparsing==3.3.2 \ | ||
| --hash=sha256:850ba148bd908d7e2411587e247a1e4f0327839c40e2e5e6d05a007ecc69911d \ | ||
| --hash=sha256:c777f4d763f140633dcb6d8a3eda953bf7a214dc4eff598413c070bcdc117cbc |
There was a problem hiding this comment.
The update to pyparsing==3.3.2 includes changes from v3.3.0 where DeprecationWarnings are now emitted for non-PEP8 compliant method names. While this is a minor version bump, it's important to check if any existing code uses these deprecated names. The pyparsing release notes mention a utility (pyparsing.tools.cvt_pyparsing_pep8_names.py) that can help in migrating to the new names, which would be beneficial for long-term maintainability and to prevent warnings in logs.
This PR contains the following updates:
==3.2.5→==3.3.2Release Notes
pyparsing/pyparsing (pyparsing)
v3.3.2Compare Source
Defined pyparsing-specific warning classes so that they can be selectively enabled
or disabled without affecting warnings raised by other libraries in the same Python
app:
PyparsingWarning- base warning for all pyparsing-specific warnings (inheritsfrom
UserWarning)PyparsingDeprecationWarning- warning for using deprecated features (inheritsfrom
PyparsingWarningandDeprecationWarning)PyparsingDiagnosticWarning- warning raised when pyparsing diagnostics areenabled and a diagnostic feature is used (inherits from
PyparsingWarning)Added
as_datetimeparse action topyparsing.common- a more generalizedversion of the
convert_to_datetimeparse action (supports any expression that extractsdate/time fields into "year", "month", "day", etc. results names), and validates
that the parsed fields represent a valid date and time.
Added
iso8601_date_validatedandiso8601_datetime_validatedexpressions topyparsing.common, which return a Pythondatetime.datetimeVarious performance improvements in
ParseResultsclass and core functions, with10-20% performance overall.
Added
regex_inverterweb page (using PyScript) to demonstrate using theinv_regex.pyexample.
Expanded regex forms handled by the
examples/inv_regex.pyexample:?P<name>){m,}and{,n})[^...])Added
SPy(Simplified Python) parser to examples.v3.3.1Compare Source
Marc Mueller for submitted issue and PR. Fixes #626.
v3.3.0Compare Source
===========================================================================================
The version 3.3.0 release will begin emitting
DeprecationWarningsfor pyparsing methodsthat have been renamed to PEP8-compliant names (introduced in pyparsing 3.0.0, in August,
2021, with legacy names retained as aliases). In preparation, I added in pyparsing
3.2.2 a utility for finding and replacing the legacy method names with the new names.
This utility is located at
pyparsing/tools/cvt_pep8_names.py. This script will scan allPython files specified on the command line, and if the
-uoption is selected, willreplace all occurrences of the old method names with the new PEP8-compliant names,
updating the files in place.
Here is an example that converts all the files in the pyparsing
/examplesdirectory:Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.